Switching Between Connectivity Types to Maintain Connectivity

ABSTRACT

Techniques are provided for leveraging narrowband connectivity (such as dial-up communications or other types of low bandwidth communications) to provision or configure broadband connectivity between a broadband access provider and a broadband device, such as a DSL modem or a cable modem. Specifically, because narrowband connectivity does not require advance configuration or provisioning by the host system of connectivity parameters for an access-seeking device, a modem at an access-seeking device may be leveraged to establish a narrowband connection between that device and a host system and to enable an exchange or negotiation of connectivity parameters necessary to enable future broadband connectivity. Thus, once established, the narrowband connection may be used as a conduit for communicating required provisioning information between the broadband-enabling host and the access-seeking device to enable broadband connectivity by the device in the future.

TECHNICAL FIELD

This description relates to communicating between two systems.

BACKGROUND

When two systems communicate, the systems may experience an unintendedinterruption of the communications session. To continue communicationswhen faced with such an interruption, one system must initiatecommunications to reestablish the communications session. In fact, whereone of the systems or the communication channel there between issecured, an interruption generally requires the system seeking access toresubmit authentication information before communications can bereestablished. Such interruptions often disrupt applications on one ofthe systems.

SUMMARY

In one general aspect, enabling communications between a user system andan accessible system involves detecting a communications failure in acommunications session between a user system and an accessible system.The communications session leverages a first connectivity type. A secondcommunications session between the user system and the accessible systemis established in which the second communications session leverages asecond connectivity type that differs from the first connectivity type.The second communications session is established automatically inresponse to the detected communication failure on the session leveragingthe first connectivity type.

Implementations may include one or more of the following features. Forexample, the second communications session leveraging the secondconnectivity type may be established without requiring usermanipulation. The first connectivity type may be broadband connectivity,the second connectivity type may be narrowband connectivity.

Using the second communications session leveraging the secondconnectivity type to receive connectivity information regarding thedetected communications failure, status or problem of the firstconnectivity type, status or problem of the user system, and status orproblem of the accessible system and status or problem of acommunication pathway between the user system and the accessible systemleveraging the first connectivity type.

The accessible system may be a secure system. When the accessible systemis a secure system, the receipt of authentication information from theuser system may be enabled. A token may be used to transparentlyestablish the second communications session leveraging the secondconnectivity type such that at least one of the applications making useof the first communications session is unaffected by the interruption ofthe first communications session and the establishment of the secondcommunications session.

The availability of the first connectivity type for communicationsbetween the user system and the accessible system may be detected. Athird communications session between the user system and the accessiblesystem may be established in which the third communication sessionleverages the first connectivity type. The first connectivity type maybe leveraged automatically in response to the detected availability ofthe first connectivity type. A token may be used to transparentlyestablish the third communications session leveraging the firstconnectivity type such that at least one of the applications making useof the second communications session is unaffected by the interruptionof the second communications session and the establishment of the thirdcommunications session.

In another general aspect, enabling communications between a user systemand an accessible system involves using a communications session of afirst connectivity type between the user system and the accessiblesystem. A second connectivity type is leveraged to enable communicationof connectivity information to the accessible system regarding the firstconnectivity type.

Implementations may include one or more of the features noted above andone or more of the following features. The communications session may beestablished automatically in response to a detected communicationfailure of another communications session leveraging the firstconnectivity type.

Implementations of any of the techniques discussed above may include amethod or process, an apparatus or system, or computer software on acomputer-accessible medium.

The details of one or more implementations set forth in the accompanyingdrawings and the description below. Other features will he apparent fromthe description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIGS. 1-3 are block diagrams illustrating exemplary communicationssystems capable of switching between a broadband connection and anarrowband connection.

FIG. 4 is a block diagram depicting exemplary communications between aclient system and a host system to switch between a broadband connectionand a narrowband connection in the event of an interruption in thebroadband connection.

FIGS. 5A and 5B are block diagrams illustrating exemplary communicationsbetween a client system and a host system to provide transparentswitching between a broadband connection and a narrowband connection toprovide uninterrupted access to the host system.

FIG. 6 is a block diagram showing a communications system capable ofreporting, without user intervention, a problem with a broadbandconnection.

For brevity, several elements in the figures are represented asmonolithic entities. However, as would be understood by one skilled inthe art, these elements each may include numerous interconnectedcomputers and components designed to perform a set of specifiedoperations and/or dedicated to a particular geographical region.

DETAILED DESCRIPTION

In the event of an unintentional interruption in communications using abroadband connection between a host system and a client system, anarrowband connection may be established and used until the broadbandconnection is reestablished. Once the broadband connection isreestablished, communications may use the broadband connection and thenarrowband connection may be disconnected.

FIG. 1 shows a communications system 100 that includes a client system105 having a home-networking gateway 110 and multiple home-networkeddevices 115 (“devices”) connected to each other and to thehome-networking gateway 110. The communications system 100 enables thedevices 115 to communicate with the host system 120 using the broadbandcommunications device 130 or the narrowband communications device 135 ofthe home-networking gateway 110.

The devices 115, the home-networking gateway 110, and the communicationsdevices 130 and 135 of client system 105 may he physically located in apersonal residence (e.g., a single-family dwelling, a house, atownhouse, an apartment, or a condominium). However, the location of thehome-networking gateway 110 in the personal residence does notnecessarily preclude one or more of the devices 115 from being networkedto the home-networking gateway 110 from a remote location. Similarly,the location of the home-networking gateway 110 in the personalresidence does not necessarily preclude use of one or more of thedevices 115 from outside of the personal residence or communication bythose devices with the host system 120 through the home-networkinggateway 110. For instance, the devices 115 may include one or moreportable computing devices that may be taken outside of the personalresidence and still remain connected through a wireless access point tothe home-networking gateway 110 located within the personal residence.

The home-networking gateway 110 is located logically between the devices115 and a host system 120 that is external to the client system 105. Thehost system 120 may be, for example, an Internet access provider device,an Internet service provider device, an online system proxy server, oranother external system device.

The devices 115 may include one or more general-purpose computers (e.g.,personal computers), one or more special-purpose computers (e.g.,devices specifically programmed to communicate with the home-networkinggateway 110 and/or the host system 120), or a combination of one or moregeneral-purpose computers and one or more special-purpose computers.Other examples of devices 115 include a workstation, a server, anappliance (e.g., a refrigerator, a microwave, and an oven), anintelligent household device (e.g., a thermostat, a security system, aheating, ventilation and air conditioning (HVAC) system, and a stereosystem), a device, a component, other physical or virtual equipment, orsome combination of these elements capable of responding to andexecuting instructions within the system architecture.

As illustrated by FIG. 1, examples of devices 115 may include, but arenot limited to, a personal computer with a Windows™ OS 115 a, aMacintosh™ personal computer 115 b, a TV set-top box 115 c, a gamedevice 115 d, a home appliance 115 e, a laptop or otherwise portablecomputer 115 f, a personal digital assistant (PDA) 115 g, and a wirelessaccess point (WAP) 115 h. Some of the devices, such as a personalcomputer with Windows™ OS 115 a, a Macintosh™ personal computer 115 b, aTV set-top box 115 c, a game device 115 d, and a home appliance 115 e,typically communicate with the home-networking gateway 110 through awired network.

Some of the other devices, such as a laptop computer 115 f and a PDA 115g, typically communicate with the home-networking gateway 110 using awireless access point 115 h. When a device communicates using wirelessaccess point 115 h, the device may be referred to as a wireless device.Wireless devices may include, but may not be limited to portabledevices. For example, a desktop personal computer, such as a personalcomputer with a Windows™ OS 115 a or a Macintosh™ personal computer 115b, may communicate using wireless access point 11511. Typically, thewireless access point 115 h is connected to home-networking gateway 110through the wired network, such that the wireless access point 115 htransmits to the home-networking gateway 110 communications receivedover a wireless communications pathway from wireless devices.

A wireless communications pathway may use various protocols tocommunicate from a wireless device to a wireless access point 115 h. Forexample, the wireless communications pathway may use wireless technologybased on the Institute of Electrical and Electronics Engineers, Inc.(IEEE) 802.11 standard (such as 802.11b or 802.11a). The wirelesscommunications pathway also may use wireless technology based on theBluetooth approach for short range wireless communications, otherpersonal area network (PAN) technologies, or other wireless technology,such as the HiperLan2 standard by the European TelecommunicationsStandards Institute (ETSI).

Some of the devices 115, such as personal computer with Windows™ OS 115a, Macintosh™ personal computer 115 b, laptop computer 115 f, and PDA115 g, include software for logging on to the host system 120 using aparticular client application that is associated with, or thatidentifies, the user of the device. Such devices may be referred to asclient devices. Other devices, such as home appliance 115 e, may includesoftware for logging on to host system 120 without identifying anassociated user of the device. Yet other devices, such as TV set-top 115c and game device 115 d, may be configured to function either as aclient device or a non-client device depending on the function beingperformed.

The home-networking gateway 110 may include a home gateway device, suchas a gateway, a router, or another communication device. Thehome-networking gateway 110 also may include a digital hub capable ofreceiving broadcast video signals, receiving communication data (such asthrough a broadband connection), and distributing the signals and datato devices 115. The home-networking gateway 110 may include anothercommunications device and/or a home entertainment device, such as astereo system, a radio tuner, a TV tuner, a portable music player, apersonal video recorder, and a gaming device.

The home-networking gateway 110 may communicate with the host system 120over broadband communications links 140. The home-networking gateway 110typically connects to the host system 120 using a broadbandcommunications device 130. Examples of the broadband communicationsdevice 130 may include (and are not limited to) a cable modem 130 a anda DSL modem 130 b. The broadband communications links 140 may includevarious types of communication delivery systems that correspond to thetype of broadband communications device 130 being used. For example, ifthe home-networking gateway 110 includes a cable modem 130 a tocommunicate with the host system 120, the cable modem 130 a typicallyuses the CMTS 140 a to deliver and receive communications from the hostsystem 120. In contrast, the DSL modem 130 h typically delivers andreceives communications with the host system 120 through a DigitalSubscriber Line Access Multiplexer (DSLAM) 140 b and an AsynchronousTransfer Mode (ATM) network 140 c.

The home-networking gateway also may communicate with host system 120using a narrowband communications device 135. Examples of the narrowbandcommunications device 135 may include (and are not limited to) an analogmodem 135 a and a satellite modem 135 b. The home-networking gateway 110uses the narrowband communications device 135 to communicate with thehost system 120 through narrowband communications links 180. Thenarrowband communications links 180 may include various types ofcommunication delivery systems that correspond to the type of narrowbandcommunications device 135 being used. For example, the analog modern 135a may use the Public Switched Telephone Network (PSTN) 180 a (which alsomay be referred to as the Plain Old Telephone Service or POTS). When thehome-networking gateway 110 includes a satellite modem 135 b, then thecommunications from a device 115 and an associated home-networkinggateway 110 may be delivered to the host system 120 using a satellitedish 180 b and a satellite 180 c.

The communications system 100 may use various protocols to communicatebetween the devices 115 and the home-networking gateway 110 and betweenthe home-networking gateway 110 and the host system 120. For example, afirst protocol may be used to communicate between the devices 115 andthe home-networking gateway 110, and a second protocol may he used tocommunicate between the home-networking gateway 110 and the host system120, where the first protocol and the second protocol may be the same ordifferent protocols. As such, the home-networking gateway 110 mayinclude different hardware and/or software modules to implementdifferent home networking system protocols.

The home-networking gateway 110 may include broadband configurationinformation 110 a that may include information for establishing and/orusing a broadband connection to communicate with the host system 120.Broadband configuration information may include a media access control(MAC) address for the broadband communications device 130; a useraccount, a password, a realm string or another type of identifyinginformation for the broadband account; and a network address (such as anInternet Protocol (IP) address) used to establish a broadband connectionbetween the home-networking gateway 110 and the host system 120. Thebroadband configuration information 110 a may he stored in a table or alist on the home-networking gateway 110.

The home-networking gateway 120 also may store narrowband configurationinformation 110 b. The narrowband configuration information 110 b mayinclude connectivity parameters (such as a username and password), oneor more access telephone numbers, and other information to establish anarrowband connection with the host system 120. The home-networkinggateway configuration information 110 b may be stored in a table or alist on the home-networking gateway 110.

The home-networking gateway 110 also may store home-networking gatewayconfiguration information 110 c that may include identifying infoillation associated with the home-networking gateway 110, such as a MACaddress. The home-networking gateway configuration information 110 calso may include device information associated with each device, such asone of devices 115, that may connect to the home-networking gateway 110.The device information may include a device identifier for the device,such as its MAC address, a network address (such as a static IP addressassociated with the device or a dynamic IP address), or other type ofhardware device identifier. The dynamic IP address may be assigned to adevice by the home-networking gateway 110 or by some other networkdevice through the Dynamic Host Configuration Protocol (DHCP) or anotherprotocol that enables the dynamic allocation of an IP address to adevice on a network.

The device information associated with each device also may include, forexample, the type of device (e.g., a client or a non-client device), theclass of device (e.g., a gaming device, a personal computer, or a PDA),the type of platform (e.g., the type of hardware, such as a Macintosh™personal computer, a Windows™-based personal computer, a PDA, a homeappliance, or an entertainment device), and/or the operating environment(e.g., the operating system type and/or version).

In addition, the device information may include a user-assigned name.The user-assigned name may be referred to as a familiar name or anickname. For example, an identifier for a particular game device may beassociated with the user-assigned name of “Billy's game device.” Thedevice information also may include parental control information orother types of access restrictions that are associated with the device.

The home-networking gateway configuration information 110 c may includeprotocol information necessary to configure the home-networking gateway110 to communicate with devices 115, such as information describing howto establish communications with one or more of devices 115, how toconfigure the wireless access point 115 h, or how to configure wirelessdevices, such as the laptop computer 115 h or the PDA 115 g using thewireless configuration information. Wireless configuration informationmay include a security key, such as a wired equivalent privacy (WEP) keythat may be used to encrypt and decrypt transmitted data, and a wirelessnetwork name, such as a service set identifier (SSID) that identifiesthe particular network. The wireless configuration information mayinclude other configuration information, such as a level of encryption(e.g., 40-bit encryption or 128-bit encryption) associated with a WEPkey.

The home-networking gateway configuration information 110 c may includea list of devices that are permitted access to the home network. Forexample, the home-networking gateway configuration information 110 a mayinclude a list of MAC addresses that uniquely identify the devices thatare permitted access to the home network.

Additionally or alternatively, the home-networking gateway 110 maycommunicate with devices using only a wireless communications pathway.In other implementations, the home-networking gateway 110 maycommunicate with devices using only a wired communications pathway.

In some implementations the broadband communications device 130 and/orthe narrowband communications device 135 may be external to thehome-networking gateway 110 in addition to, or in lieu of, the broadbandcommunications device 1.30 and the narrowband communications device 135included in the home-networking gateway 110, as shown in FIG. 1. When acommunications device is included in the home-networking gateway, thetwo devices may be said to be “integrated” (e.g., the home-networkinggateway may be said to include an integrated communications device).Similarly, in some implementations, a wireless access point 115 h may beincluded in the home-networking gateway 110 in lieu of, or in additionto, wireless access point 115 h that is external to the home-networkinggateway 110, as shown in FIG. 1.

The home-networking gateway 110 may be configured to automaticallyestablish a narrowband connection between the client system 105 and thehost system 120 in the event of an unintentional interruption incommunications using a broadband connection established between the hostsystem 120 and the client system 105. The client system 105 may use thenarrowband connection for communications with the host system 120 untilthe broadband connection is available/reestablished. Once broadbandaccess is available, the home-networking gateway 110 may automaticallyreestablish broadband connectivity for communications between the clientsystem 105 and the host system 120 and may disconnect the narrowbandconnection with the host system 120.

In some implementations, the home-networking gateway 110 may beconfigured to automatically establish the narrowband connection in theevent of an unintended interruption of a broadband connection such thatat least one of the applications making use of the broadbandcommunications session is unaffected by the interruption and thereestablishment of the communications session using the narrowbandconnection.

In some implementations, the home-networking gateway 110 also may beconfigured to provide, automatically without user manipulation,information regarding the problem(s) leading or incident to aninterruption in the broadband connectivity. The home-networking gateway110 may send a message to the host system 120 to report the problem withthe broadband connection, or the home-networking gateway 110 may connectdirectly to a problem reporting system of the host system 120 to reportthe problem.

FIG. 2 illustrates a communications system 200 including a client system205 communicating with a host system 220. In contrast with thecommunications system 100 of FIG. 1, the communications system 200 doesnot include as part of the client system 205 a home-networking gateway,such as home-networking gateway 110.

The host system 220 includes a host device 222 and a host controller224. The host device 222 and the host controller 224 each typicallyinclude one or more hardware components and/or software components. Anexample of a host device 222 is a general-purpose computer capable ofresponding to and executing instructions in a defined manner. Otherexamples include a special-purpose computer, a workstation, a server, adevice, a component, or other physical or virtual equipment or somecombination thereof capable of responding to and executing instructions.

An example of the host controller 224 is a software application loadedon the host device 222 for commanding and directing communicationsenabled by the host device 222. Other examples include a program, apiece of code, an instruction, a device, a computer, a computer system,or a combination thereof, for independently or collectively instructingthe host device 222 to interact and operate as described. The hostcontroller 224 may be embodied permanently or temporarily in any type ofmachine, component, physical or virtual equipment, storage medium, orpropagated signal capable of providing instructions to the host device222.

The client system 205 communicates with the host system 220 throughcommunications links 230. The communications link 230 may include orleverage communications pathways 232, 234, enabling communicationsthrough the one or more delivery networks 236. Examples of a deliverynetwork include the Internet, the World Wide Web, WANs, LANs, analog ordigital wired and wireless telephone networks (e.g., PSTN (“PublicSwitched Telephone Network”), ISDN (“Integrated Services DigitalNetwork”), and DSL (“Digital Subscriber Line”) including various formsof DSL such as SDSL (“Single-line Digital Subscriber Line”), ADSL(“Asymmetric Digital Subscriber Loop), HDSL (“High bit-rate DigitalSubscriber Line”), and VDSL (“Very high bit-rate Digital SubscriberLine), radio, TV, cable, satellite, and/or any other delivery mechanismfor carrying data. Each of the communications pathways 232, 234 mayinclude, for example, a wired, wireless, cable or satellitecommunications pathway.

The client system 205 typically includes a general purpose computer 270having an internal or external storage 272 for storing data and programssuch as an operating system 274 (e.g., DOS, Windows®, Windows® 95,Windows® 98, Windows® 2000, Windows® NT, Windows® Millennium Edition,Windows® XP, OS/2, Macintosh OS, and Linux) and one or more applicationprograms. Examples of application programs include authoringapplications 276 (e.g., word processing, database programs, spreadsheetprograms, presentation programs, and graphics programs) capable ofgenerating documents or other electronic content; client applications278 (e.g., an America Online (AOL) client, CompuServe client, AmericaOnline Instant Messaging (AIM) client, AOL TV (“television”) client, andan Internet service provider (ISP) client) capable of communicating withother computer users, accessing various computer resources, and viewing,creating, or otherwise manipulating electronic content; and browserapplications 280 (e.g., Netscape's Navigator and Microsoft's InternetExplorer) capable of rendering standard Internet content.

The general-purpose computer 270 also includes a central processing unit282 (CPU) for executing instructions in response to commands from theclient controller 283. In one implementation, the client controller 225includes one or more of the application programs installed on theinternal or external storage 272 of the general-purpose computer 270. Inanother implementation, the client controller 225 includes applicationprograms externally stored in and executed by one or more device(s)external to the general- purpose computer 270.

The general-purpose computer typically includes a broadbandcommunications device 284, such as the cable modem 130 a or the DSLmodem 130 b of FIG. 1, and a narrowband communications device 285, suchas a analog modem 135 a and a satellite modem 135 b of FIG. 1, forsending and receiving data. Other examples of a communications device284 or 285 include a transceiver, a set-top box, a communication card, asatellite dish, an antenna, or another network adapter capable oftransmitting and receiving data over the communications link 230 througha wired or wireless data pathway 232.

The general-purpose computer 270 also may include a TV (“television”)tuner 286 for receiving television programming in the form of broadcast,satellite, and/or cable TV signals. As a result, the client device 220can selectively and/or simultaneously display network content receivedby communications device 284 or 285 and television programming contentreceived by the TV tuner 286.

The general-purpose computer 270 typically includes an input/outputinterface 288 to enable a wired or wireless connection to variousperipheral devices 290, Examples of peripheral devices 290 include, butare not limited to, a mouse 291, a mobile phone 292, a personal digitalassistant 293 (FDA), a keyboard 294, a display monitor 295 with orwithout a touch screen input, and/or a TV remote control 296 forreceiving information from and rendering information to subscribers.Other examples may include voice recognition and synthesis devices.

Although FIG. 2 illustrates devices such as the mobile telephone 292,the PDA 293, and the TV remote control 296 as being peripheral withrespect to the general-purpose computer 270, in another implementation,such devices may themselves include the functionality of thegeneral-purpose computer 270 and operate as the client device 220. Forexample, the mobile phone 292 or the FDA 293 may include computing andnetworking capabilities, and may function as a client device 220 byaccessing the delivery network 230 and communicating with the hostsystem 220. Furthermore, the client system 205 may include one, some,all, or none of the components and devices described above.

The client system 205 may be configured to automatically establish anarrowband connection with the host system 220 in the event of anunintentional interruption in communications using a broadbandconnection. The client system 205 may use the narrowband connection forcommunications with the host system 220 until the broadband connectionis reestablished. Once broadband access is available, the client system205 may automatically reestablish broadband connectivity forcommunications with the host system 220 and may disconnect thenarrowband connection with the host system 220.

In some implementations, the client system 205 may be configured toautomatically establish the narrowband connection in the event of anunintended interruption of a broadband connection such that at least oneof the applications making use of the broadband communications sessionis unaffected by the interruption and the reestablishment of thecommunications session using the narrowband connection. For example, anapplication making use of the broadband communications may be unaffectedby the interruption and reestablishment when the application is notaffected operationally or when it is affected only by the potential of achange in processing speed or responsiveness to user manipulation. Insuch cases, the application does not fail, become inoperative, or reportan error to the user of the application. A user of the application maybecome aware of a communication speed change that may result fromswitching from a broadband connectivity type to a slower narrowbandconnectivity type. The user may experience delay or greater responsetime in the application even though the user does not experience anapplication failure or operational error.

Additionally, the client system 205 also may be configured toautomatically report the problem with broadband connectivity. The clientsystem 205 may send a message to the host system 220 to report theproblem with the broadband connection or may directly connect to aproblem reporting system of the host system 220 to report the problem.

FIG. 3 shows an implementation of a communications system 300 thatincludes a client system 305, a host system 320, and a communicationslink 330. The client system 305 may include one or more of an OSprotocol stack 375, a protocol server module 377, a controller module379, an optional adapter interface 381, a broadband communicationsdevice 384, and a narrowband communications device 385. The OS protocolstack 375 may be included as part of an operating system (“OS”). The OSprotocol stack 375 may be designed for or capable of enabling the OS toencapsulate data for communication. In general, the OS protocol stack375 may be implemented using a PPP (“Point-to-Point Protocol”)interface. For example, Windows™ OSs generally include a NDISWAN(“Network Device Interface Specification for Wide Area Networks”)component that functions as the PPP interface. In some Windows™ OSs andin some other types of OSs, a PPP Daemon (PPPD) may function as the PPPinterface.

The protocol server module 377 may be structured and arranged tointerface with the client device OS protocol stack 375 and thecontroller module 379. The protocol server module 377 enables the clientsystem 310 and the host system 320 to communicate through the deliverynetwork 336 using any one of several encapsulating protocols.

The protocol server module 377 may intercept and take over acommunications session that the OS protocol stack 375 attempts toinitiate with the host system 320 using a first protocol. For example,the OS protocol stack 375 may start a communications session intendingto negotiate and exchange configuration data with the host system 320using the first protocol. Instead, the protocol server module 377 may“spoof” the host system 320 and intercept the communications sessionfrom the OS protocol stack 375, rather than having the OS protocol stack375 communicate directly with the host system 320. The spoofingtypically is transparent to the OS protocol stack 375 and the hostsystem 320. By capturing the communications session at the protocolserver module 377, the protocol server module 377 may negotiate aseparate or a substitute communications session with the host system 320using a second protocol that is different from the first protocol. Basedon this second protocol, data from the OS protocol stack 375 may berouted to the host system 320 over the separate or substitutecommunications session. Similarly, the protocol server module 377 may beused to spoof the OS protocol stack 375 from the perspective of the hostsystem 320 such that the host system 320 may unknowingly and/orunintentionally transmit to the protocol server module 377 theconfiguration and/or other data that is destined for the OS protocolstack 375 under the second protocol. The protocol server module 377 thenmay transport this data to the OS protocol stack 375 using the firstprotocol.

Data packets that are destined to be communicated between the OSprotocol stack 375 and the host system 320 are translated by theprotocol server module 377 between the first protocol and the secondprotocol. For example, when the data packets include encapsulation, theprotocol server module 377 may translate the data packets by removingthe encapsulation from the data packets. Additionally or alternatively,the protocol server module 377 may translate the data packets byencapsulating previously unencapsulated data packets or re-encapsulatingpreviously encapsulated data packets using any one of severalcommunications protocols.

The protocol server module 377 may interface directly with the OSprotocol stack 375, or the client system 305 may further include aninterface adapter 381 that the protocol server module 377 uses tointerface with the OS protocol stack 375. For instance, in some OSs inwhich the OS protocol stack 375 is implemented using a PPPD, theprotocol server module 377 may interface directly with the PPPD withoutthe need for an interface adapter 317. By contrast, in other OSs, suchas the Windows™ OS, in which the OS protocol stack 375 is implementedusing NDISWAN, the adapter interface 381 may be used to interface theprotocol server module 377 and the NDIS WAN protocol stack. Morespecifically, for example, a WAN (“Wide Area Network”) Miniport adapter381 may be used as a virtual modem to interface the protocol servermodule 377 and the NDISWAN.

In one implementation, the protocol server module 377 may include a PPP(“Point-to-Point Protocol”) server module. When the protocol servermodule 377 functions as a PPP server module, it may capture a PPPcommunications session between the OS protocol stack 375 and the hostsystem 320. The PPP server module also negotiates a PPP communicationssession with the OS protocol stack 375. The PPP server module maytranslate PPP data packets from the OS protocol stack 375 destined forthe host system 320. For example, the protocol server module 377 maytranslate the data packets by removing the PPP encapsulation. The datapackets may include data packets in a format consistent with, forexample, Internet Protocol (IP) data, Transmission Control Protocol(TCP) data, other data capable of being encapsulated by an encapsulatingprotocol, or a combination of these data formats. The data packets mayinclude Layer Three data packets. After removing the PPP encapsulation,the PPP server module may encapsulate the packets in any one of severalencapsulating protocols (e.g., PPP, UDP (“User Datagram Protocol”), L2TP(“Layer Two Tunneling Protocol”), and PPP over Ethernet (“PPPoE”)).Additionally, the protocol server module 377 may translate data packetsfrom the host system 320 by removing the encapsulation from the datapackets and encapsulating the packets in PPP, and then may transport thepackets to the client device OS protocol stack 375.

The protocol server module 377 may be configured to enable the clientsystem 305 to communicate with the host system 320 using variousencapsulating protocols that are supported by the delivery network 336and the host system 320, regardless of whether these protocols areotherwise supported by the client system 305. For instance, although aclient system 305 may support only a PPP encapsulating protocol throughits OS protocol stack 375, the protocol server module 377 may functionto enable the client system 305 to communicate through the deliverynetwork 336 with the host system 320 using other encapsulatingprotocols. In a more specific example, the protocol server module 377generally enables the client system having only a PPP protocol interfaceto communicate with the host system 320 using, for example, L2TP, PPP,PPPoE, UDP tunneling, token tunneling (e.g., a P3 tunnel), any otherencapsulating protocols and tunneling mechanisms, or a combination ofthese encapsulating protocols and tunneling mechanisms.

The protocol server module 377 may be implemented as a clientapplication or as a software module within a client application.Examples of client applications include AOL (“America Online”) client, aCompuServe client, an AIM (“America Online Instant Messenger”) client,an AOL TV (“America Online Television”) client, and an ISP (“InternetService Provider”) client capable of communicating with other computerusers, accessing various computer resources, and viewing, creating, orotherwise manipulating electronic content). The encapsulation may beperformed by the protocol server module 377, or alternatively, it may beperformed by a separate client application (e.g., PPP client, UDPclient, PPPoE client, L2TP client, or AOL client).

Additionally, the protocol server module 377 may be configured to enablethe client system 305 to automatically switch between broadband andnarrowband connections in the event of an unintentional interruption incommunications using a broadband connection. The protocol server module377 may be further configured in some implementations to enable theclient system 305 to automatically establish the narrowband connectionin the event of an unintended interruption of a broadband connectionsuch that at least one of the applications making use of the broadbandcommunications session is unaffected by the interruption and thereestablishment of the communications session using the narrowbandconnection. Additionally or alternatively, in some implementations, theprotocol server module 377 may be configured to enable the client system305 to automatically report the problem with broadband connectivity.

The controller module 379 may be logically connected to the protocolserver module 377 and may be structured and arranged to controlcommunications between the OS protocol stack 375, the protocol servermodule 377, and the host system 320. The controller module 379 may beimplemented as a client application or as a software module within aclient. Additionally, the controller module 379 may function to controlthe broadband communications device 384 and/or the narrowbandcommunications device 385.

The broadband communications device 384 and the narrowbandcommunications device 385 each typically has the attributes of andincludes one or more of the communications devices described above withrespect to communications devices 130 and 135 of FIG. 1.

The communications link 330 may include communications pathways 332, 334that enable communications through the one or more delivery networks336. The delivery network 336 that provides a direct or an indirectcommunications path between the client system 305 and the host system320, irrespective of physical separation. Examples of a delivery network336 include the Internet, the World Wide Web, WANs, LANs, analog ordigital wired and wireless telephone networks (e.g., PSTN (“PublicSwitched Telephone Network”), ISDN (“Integrated Services DigitalNetwork”), and DSL (“Digital Subscriber Line”) including various formsof DSL such as SDSL (“Single-line Digital Subscriber Line”), ADSL(“Asymmetric Digital Subscriber Loop), HDSL (“High bit-rate DigitalSubscriber Line”), and VDSL (“Very high bit-rate Digital SubscriberLine), radio, TV, cable, satellite, and/or any other delivery mechanismfor carrying data. Each of the communications pathways 332, 334 mayinclude, for example, a wired, wireless, cable or satellitecommunications pathway.

FIG. 4 shows an exemplary process 400 between a client system 405 and ahost system 420 that automatically switches between a broadbandconnection and a narrowband connection to provide network access in theevent of a disruption of the broadband connection. The client system405, for example, may be an implementation of the home-networkinggateway 110 or the client system 105 both of FIG. 1, the client system205 of FIG. 2, or the protocol server module 377 or client system 305both of FIG. 3. The host system 420, for example, may be animplementation of the host system 320 of FIG. 1, the host system 220 ofFIG. 2, or the host system 320 of FIG. 3.

The procedure 400 begins when a communications session using a broadbandconnection is established between the host system 420 and the clientsystem 405 (step 430). The establishment of the communications sessionmay include having the host system 420 authenticate the client system405 and/or and provide a communication address for the broadbandconnection.

More specifically, the establishment of the communications session (step430) may be initiated, for example, when the client system 410 submits arequest for access to the host system 420. The host system 420 mayrequest authentication information from the client system 405, whichreceives the authentication request and submits the requestedauthentication information. Authentication information may include auser identifier (such as, for example, a user name, a screen name, or aphone number) and access password (such as, for example, a subscriberpassword or personal identification number (“PIN”)), which may be usedto authenticate the client system as authorized. The host system 420receives the authentication information and authenticates the clientsystem.

During the establishment of the communications session (step 430), thehost system 420 may provide a host-designated communications address tothe client system 405. The host-designated communications address maybe, for example, an Internet Protocol address. Alternatively, thecommunications address may be a port that has been assigned by a NetworkAddress Translator (NAT). The communications address may be a numericalor alphabetical address (such as a domain name).

When the client system 405 and the host system 420 experience aninterruption in the communications session (step 444), the client system405 detects the interruption (step 447 c). The interruption in thecommunications session may occur when the communications sessionfails—that is, the communication session is interrupted due to adisconnection between the client system 405 and the host system 420. Thecommunications session failure may occur because of a problem with theclient system 405, the host system 420, or the communication pathwaybetween the client system 405 and the host system 420.

When the client system 405 includes a home-networking gateway thatincludes an integrated broadband communications device, such ashome-networking gateway 110 of FIG. 1 that includes a DSL modem, theclient system 405 may detect the interruption of the broadbandconnection by detecting the loss of the ATM link. When the client system505 does not include a home-networking gateway with an integratedbroadband communications device, the interruption in the broadbandconnection may be detected by, for example, a failure in an attempt tocommunicate with the host system 420 or the receipt of a notice offailure from an application running on the client system 405. The clientsystem 405 also may detect the interruption in the broadband connectionwhen monitoring the broadband connection. For example, the client system405 may periodically attempt to contact the host system 420 through thebroadband connection (e.g., send a ping to the host system 420 and waitfor a reply). When a response is not received from the host system 420,the client system detects an interruption in the broadband connectionwith the host system 420.

Additionally or alternatively, the client system 405 may inform the userof the client system 405 about the interruption, for example, bydisplaying a message. Informing the user of the client system 405 of theinterruption may he beneficial, for example, when the client systemdials a modem to reestablish a connection with the host system so thatthe user is not surprised by the sound of the modem dialing.

The client system 405 initiates a narrowband connection with the hostsystem 420 and requests narrowband access from the host system (step 455c). This may be accomplished, for example, when the client system 405uses a narrowband communications device to establish a narrowbandconnection, such as a dial-up connection, with the host system 420. Insome implementations, identification information (such as user name) maybe sent to the host system 420 from the client system 405 when thenarrowband connection is initiated. in other implementations,identification information may be sent later, as described below withrespect to steps 457 h-460 h.

The host system 420 receives the request for narrowband access (step 455h). The receipt of the request for narrowband access may enable the hostsystem 420 to detect the communications session interruption when thehost system 420 has not yet otherwise detected the interruption of thecommunications session.

The host system may request authentication information from the clientsystem 405 (step 457 h), and if so, the client system 405 receives theauthentication request (step 457 c) and submits authenticationinformation using the narrowband connection (step 460 c). This may beaccomplished, for example, by submitting narrowband configurationinformation stored on the client system, such as narrowbandconfiguration information 110 b of FIG. 1. The host system 420 receivesthe authentication information (step 460 h).

If the host system 420 has not yet otherwise detected the interruptionof the communications session, receiving authentication information froma client system 405 may enable the host system 420 to detect thecommunications session interruption. The steps 457 h-460 h may bereferred to as sub-process 462, which may be optionally performed. Insome implementations, the request for narrowband access from the clientsystem 405 may include authentication information so as to obviate theneed for sub-process 462.

The host system 420 authenticates the client system 405 (step 464 h).

The client system 405 and the host system 420 exchange communicationsusing the narrowband connection (step 470). Optionally, the clientsystem 405 may provide, without user intervention, information regardingthe problem(s) leading or incident to an interruption in the broadbandconnection to the host system 420 (step 474 c). This may beaccomplished, for example, by the client system 405 sending anelectronic mail message or other type of communication to the hostsystem 420 to provide the information regarding the broadbandconnection. For example, the client system 405 may send an electronicmail (“email”) message to a designated email address to report the lossof the broadband connection. The client system 405 may includeinformation about the trouble or about the connection within the emailmessage. For example, the client system 405 may include diagnosticinformation about the broadband device in the email message.Alternatively or additionally, the client system 405 may report the lossof the broadband connection directly to the host system 420 byconnecting to an application program or host service for that purpose(e.g., a trouble-reporting application for technical support or a callcenter). The client system 405 also may connect directly to a problemreporting system of the host system 420 to provide the information.

When the broadband connection again becomes available (step 475) and theclient system 405 detects availability of the broadband connection (step477 c), the client system 405 initiates the establishment ofcommunications using the broadband communications (step 490) anddisconnects the narrowband connection (step 495 c). The client system405 may detect the availability of the broadband connection, forexample, by periodically trying to establish a broadband connection withthe host system. When the client system 405 includes a home-networkinggateway with an integrated DSL modem, such as the home-networkinggateway 110 depicted in FIG. 1, the home-networking gateway may be ableto detect the availability of the broadband connection based on thereestablishment of the underlying ATM link. When the client system 405does not include a home-networking gateway with an integrated broadbandcommunications device, the client system 405 may use an activemonitoring process to detect the availability of the broadbandconnection. One example of an active monitoring process is when theclient system 405 periodically tries to contact the host system 420through the broadband connection (e.g., sends a ping to the host system420 and waits for a reply). When the client system 405 receives aresponse from the host system 420, the client system determines that thebroadband connection is available.

FIGS. 5A and 5B depict a process 500 to provide transparent reconnectionof a communications session between the client system 505 and the hostsystem 520 when the broadband connection is interrupted. The clientsystem 505, for example, may be an implementation of the home-networkinggateway 110 or the client system 105 both of FIG. 1, the client system205 of FIG. 2, the protocol server module 377 or client system 305 bothof FIG. 3, or the client system 410 of FIG. 4. The host system 520, forexample, may be an implementation of the host system 120 of FIG. 1, thehost system 220 of FIG. 2, the host system 320 of FIG. 3, or the hostsystem 420 of FIG. 4.

The procedure 500 begins when a communications session using a broadbandconnection is established between the host system 520 and the clientsystem 505, as described previously with respect to step 430 of FIG. 4(step 530).

The client system 505 requests a reconnection token (step 535 c), whichmay be used to reestablish communications between the client system 505and the host system 520 after an unintentional interruption of thecommunications session. The reconnection token may be valid only for twosubmissions and may be valid only for a period of time, usually a shortperiod of time, following an interrupted communications session.

The host system 520 receives the token request (step 535 h). The hostsystem 520 generates the reconnection token (step 537 h). The generationof the reconnection token may include relating the reconnection token tothe host-designated communications address, storing the reconnectiontoken, the host-designated communication address and the relationshipbetween the reconnection token and address.

The host system 520 provides the reconnection token to the client system(step 538 h), which receives (step 538 e) and stores the token (step 540c).

When the client system 505 and the host system 520 experience aninterruption in the communications session (step 545), the client system505 or the host system 520 may detect the interruption (steps 547 c and547 h). However, to enhance security, it may be possible to limitdetection of the interruption to the host system, thus reducing theopportunities for spoofing of authentic tokens.

When the host system 520 detects the interruption based on criteriaother than receipt of an access request or token from a disconnectedclient system (step 547 h), the host system reserves the communicationsaddress used in the interrupted communications session during the periodof interruption (step 550 h). The host system may limit the duration ofthe reservation for a specific period of time (which may be referred toas the lifespan of the token) that is measured from the time ofcommunications session interruption. This may be accomplished, forexample, by having a list or table of issued reconnection tokens andstoring the client system to which the reconnection token was issued andthe time of interruption, if any, for each issued reconnection token.

If, during the lifespan of the reconnection token, the host system 520receives a request for access from the client system 505 without theclient system submitting the reconnection token, the host system 520 maytake any of several actions, including terminating the sessionimmediately, continuing to wait for the submission of the reconnectiontoken or the expiration of the lifespan of the reconnection token, andproviding access using a host-designated communication address that isnot the same as the reserved communication address.

The client system 505 detects an unintentional interruption of thebroadband connection, such as described previously with respect to step447 c of FIG. 4 (step 547 c). The client system 505 initiates anarrowband connection with the host system 520 and requests narrowbandaccess from the host system, such as described previously with respectto step 455 c of FIG. 4 (step 555 c). The host system 520 receives therequest for narrowband access (step 555 h) and requests authenticationinformation from the client system 505 (step 557 h), such as describedpreviously with respect to steps 455 h and 457 h of FIG. 4.

The client system 505 receives the authentication request (step 557 c)and submits the reconnection token using the narrowband connection withthe host system 520 (step 560 c). More specifically, the client systemmay determine whether a reconnection token exists, retrieve thereconnection token from storage, and send the reconnection token to thehost system. The reconnection token may be submitted automatically inlieu of or in addition to authentication information, unprompted, or inresponse to a request from the host system. Such a process generallypreempts or replaces the display of a user interface solicitingreconnection or reauthentication information from a user.

Alternatively, the client system 505 may submit the reconnection tokenwhen the client system 505 initiates the narrowband connection andrequests access to the host system 520.

The host system 520 receives the authentication information in the formof the token (step 560 h). If the host system 520 has not yet otherwisedetected the interruption of the communications session, receivingauthentication information from a client system 505 using a reconnectiontoken may enable the host system 520 to detect the communicationssession interruption.

Referring also to FIG. 5B, the host system 520 responds to receipt ofauthentication information by authenticating the client system (step 565h), which may involve determining whether the reconnection tokensubmitted by the client system is valid (such as, by comparing thereceived reconnection token with a list of issued tokens, by looking upthe reconnection token in a table that lists all valid reconnectiontokens, or, if the reconnection token is time-limited or use-limited,determining whether it is expired). The host system 520 then providesaccess using the same communications address which was used in theinterrupted broadband communications session in order to reestablishcommunications with the client system 505 (step 567 h).

The client system 505 receives reconnection access such that at leastone of the client applications making use of the communication sessiondoes not experience a disruption despite the communications sessioninterruption; that is, at least one client application is unaffected bythe interruption and the associated reconnection, which has beendescribed previously with respect to FIG. 2 (step 567 c). Moreover, someoperating systems may terminate a client application upon loss of aconnection to the host system on which the client application depends.An operating system on the client system 505, however, may be preventedfrom terminating a client application by masking the loss of theconnection, for instance, using a local protocol module that “spoofs”the operating system protocol stack and host system, as described withrespect to FIG. 3.

In some implementations, the client system 505 may receive reconnectionaccess using the same session identifier that was associated with theinterrupted session (step 567 c).

The client system 505 and the host system 520 exchange communicationsusing the narrowband connection (step 570). Optionally, the clientsystem 505 may provide, without user intervention, information regardingthe problem(s) leading or incident to an interruption, with thebroadband connection to the host system 520, as described previouslywith respect to step 474 c of FIG. 4. When the broadband connectionagain becomes available (step 576) and the client system 505 detectsavailability of the broadband connection (step 577 c), the client system505 submits to the host system 520 the reconnection token using thebroadband connection (step 580 c). In some implementations, the hostsystem 520 may detect availability of the broadband connection (step 577c) and request from the client system 510 authentication informationand/or the reconnection token. In response, the client system 510submits the reconnection token using the broadband connection (step 580c).

The host system 520 receives authentication information from the clientsystem 505 in the form of the reconnection token (step 580 h),authenticates the client system 505 (step 585 h), and provides accessusing the reserved communication address (step 587 h). To provide accessto the client system 505 using the reserved communication address, thehost system 520 may disconnect the narrowband connection with the clientsystem 510 that used the reserved communication address.

In some implementations, the client system 505 may receive reconnectionaccess using the same session identifier that was associated with theinterrupted session.

The client system 505 receives reconnection access transparent to atleast one client application (step 587 c), as described previously withrespect to step 567 c. The client system 505 and the host system 520exchange communications using the broadband connection (step 590).

In some implementations, a single-use reconnection token may be used. Insuch a case, when the narrowband connection is established forcommunications between the host system 520 and the client system 505(steps 555 c-570 c), the client system 505 may request and be provided asecond reconnection token from the host system in a manner the same asor similar to that described previously in steps 535 c-540 c. The clientsystem 505 may use the second reconnection token to transparentlyconnect to the host system using the reestablished broadband connectionwhen the broadband connection becomes available (step 580 c).

FIG. 6 illustrates a communications system 600 capable of reporting,without user intervention, a problem with a broadband connection betweena client system and a broadband access provider. The communicationssystem 600 includes a client system 605 that has a home-networkinggateway 610 and a client device 615, a host system 620, and a broadbandaccess provider 650, and a network 655.

The client system 605 may be an implementation of the client system 105of FIG. 1. The home-networking gateway 610 generally maintains apersistent broadband connection to broadband access provider 650. Thebroadband persistent connection may be a connection using, for example,a cable modem, such as cable modem 130 a of FIG. 1, or a DSL modem, suchas DSL modem 130 b of FIG. 1.

The broadband access provider 650 provides client system 610 with accessto network 655, which may be an implementation of network 236 of FIG. 2or network 336 of FIG. 3. The broadband access provider 650 may be ahost system similar to the host system 120 of FIG. 1, the host system220 of FIG. 2, the host system 320 of FIG. 3, the host system 420 ofFIG. 4, or the host system 520 of FIGS. 5A and 5B. However, thebroadband access provider 650 receives notification of an interruption,or other type of problem, with the broadband connection between thebroadband access provider 650 and the client system 605 from the hostsystem 620.

When the client system 605 detects an interruption of the broadbandconnection with the broadband access provider 650, the client system 605establishes a transient connection (such as a narrowband or dial-upconnection) with the host system 620 using communications link 630,which may be an implementation of communications links 230 of FIG. 2.The communications link 630 may include communications pathways 632 and634 enabling communications through the one or more delivery networks636.

The client system 605 and the host system 620 may exchangecommunications that include authentication messages used to establish atrusted connection. The client system 605 notifies the host system 620of the interruption of the broadband connection with the broadbandaccess provider 650. For example, the client system 605 may send anemail message or other type of communication to the host system 620. Theclient system also may connect with a trouble reporting application ofthe host system 620 to report a problem with the broadband connection.The client system 605 may include diagnostic or other information, forexample, obtained from the broadband communications device with thenotification.

The host system 620 notifies the broadband access provider 650 of theproblem with the broadband connection. In some implementations, the hostsystem 620 may establish a persistent connection with the broadbandaccess provider 650, and it may provide that broadband access provider650 with information needed to rectify the reported problem, whichinformation may or may not he obtained or solicited from the clientsystem 605. A persistent connection may be particularly beneficial whenthe number of notifications or other types of communications routedbetween the broadband access provider 650 and the host system 620 isgreater than the capacity afforded by a transient connection thatrequires authentication to be performed when a connection isestablished.

The host system 620 and the broadband access provider 650 may he ownedor controlled by the same or different legal entities. Generally, thehost system 620 and the broadband access provider 650 are differentlegal entities.

Although the techniques have been described using a host system and aclient system, the techniques and concepts extend to systemscommunicating other than in a client and host relationship and thereforeare applicable to other contexts. For example, the benefits may beapplicable to systems that are accessible by a user system, such as asystem in a point-to-point communications system or a trusted computersystem that is not necessarily engaged in a host-client relationshipwith a user system. A system that is accessible by a user system may bereferred to as an accessible system.

Although techniques have been described using a broadband connection anda narrowband connection, the techniques and concepts may be applicableto other types of connections.

The techniques and concepts are applicable to communications devicesother than a gateway or a home-networking gateway. For example, arouter, a digital hub, a general-purpose computer, or a single-purposeconfiguration management device may perform the functions described asbeing performed by the gateway. The gateway also may be referred to as alocal proxy device.

Implementations may include a method or process, an apparatus or system,or computer software on a computer medium. It will be understood thatvarious modifications may be made that still fall within the followingclaims. For example, advantageous results still could be achieved ifsteps of the disclosed techniques were performed in a different orderand/or if components in the disclosed systems were combined in adifferent manner and/or replaced or supplemented by other components.

1. A method for enabling communications between a user system and anaccessible system, the method comprising: detecting a communicationsfailure in a communications session between a user system and anaccessible system, the communications session leveraging a firstconnectivity type; and establishing a second communications sessionbetween the user system and the accessible system, the secondcommunications session leveraging a second connectivity type thatdiffers from the first connectivity type, automatically in response tothe detected communication failure on the session leveraging the firstconnectivity type.
 2. The method of claim 1 wherein establishing thesecond communications session leveraging the second connectivity type,automatically in response to the detected communication failurecomprises establishing a second communications session leveraging thesecond connectivity type, without requiring user manipulation inresponse to the detected communications failure on the sessionleveraging the first connectivity type.
 3. The method of claim 1 whereinthe first connectivity type comprises broadband connectivity.
 4. Themethod of claim 1 wherein the second connectivity type comprisesnarrowband connectivity.
 5. The method of claim 1 further comprisingenabling the receipt, using the second communications session leveragingthe second connectivity type, of connectivity information regarding oneor more of the detected communications failure, status or problem of thefirst connectivity type, status or problem of the user system, andstatus or problem of the accessible system and status or problem of acommunication pathway between the user system and the accessible systemleveraging the first connectivity type.
 6. The method of claim 1 whereinthe accessible system comprises a secure system, the method furthercomprising enabling the receipt of authentication information from theuser system when establishing the second communications session.
 7. Themethod of claim 1 further comprising using a token to transparentlyestablish the second communications session leveraging the secondconnectivity type such that at least one of the applications making useof the first communications session is unaffected by the interruption ofthe first communications session and the establishment of the secondcommunications session.
 8. The method of claim 1 further comprising:detecting availability of the first connectivity type for communicationsbetween the user system and the accessible system; and establishing athird communications session between the user system and the accessiblesystem, the third communication session leveraging the firstconnectivity type, automatically in response to the detectedavailability of the first connectivity type.
 9. The method of claim 1further comprising using a token to transparently establish the thirdcommunications session leveraging the first connectivity type such thatat least one of the applications making use of the second communicationssession is unaffected by the interruption of the second communicationssession and the establishment of the third communications session.
 10. Amethod for enabling communications between a user system and anaccessible system, the method comprising: using a communications sessionof a first connectivity type, between the user system and the accessiblesystem; and leveraging a second connectivity type to enablecommunication of connectivity information to the accessible systemregarding the first connectivity type.
 11. The method of claim 10wherein the communications session is established automatically inresponse to a detected communication failure of another communicationssession leveraging the first connectivity type.
 12. The method of claim11 wherein the connectivity information comprises connectivityinformation relating to one or more of the one or more of the detectedcommunications failure, status or problem of the first connectivitytype, status or problem of the user system, and status or problem of theaccessible system and status or problem of a communication pathwaybetween the user system and the accessible system leveraging the firstconnectivity type.
 13. A computer-readable medium or propagated signalhaving embodied thereon a computer program configured to enablecommunications between a user system and an accessible system, themedium or signal comprising one or more code segments configured to:detect a communications failure in a communications session between auser system and an accessible system, the communications sessionleveraging a first connectivity type; and establish a secondcommunications session between the user system and the accessiblesystem, the second communications session leveraging a secondconnectivity type that differs from the first connectivity type,automatically in response to the detected communication failure on thesession leveraging the first connectivity type.
 14. The medium of claim13 wherein the one or more code segments configured to establish thesecond communications session leveraging the second connectivity type,automatically in response to the detected communication failure compriseone or more code segments configured to establish a secondcommunications session leveraging the second connectivity type, withoutrequiring user manipulation in response to the detected communicationsfailure on the session leveraging the first connectivity type.
 15. Themedium of claim 13 wherein the first connectivity type comprisesbroadband connectivity.
 16. The medium of claim 13 wherein the secondconnectivity type comprises narrowband connectivity.
 17. The medium ofclaim 13 wherein the one or more code segments are further configured toenable the receipt, using the second communications session leveragingthe second connectivity type, of connectivity information regarding oneor more of the detected communications failure, status or problem of thefirst connectivity type, status or problem of the user system, andstatus or problem of the accessible system and status or problem of acommunication pathway between the user system and the accessible systemleveraging the first connectivity type.
 18. The medium of claim 13wherein: the accessible system comprises a secure system, and the one ormore code segments are further configured to enable the receipt ofauthentication information from the user system when establishing thesecond communications session.
 19. The medium of claim 13 wherein theone or more code segments are further configured to use a token totransparently establish the second communications session leveraging thesecond connectivity type such that at least one of the applicationsmaking use of the first communications session is unaffected by theinterruption of the first communications session and the establishmentof the second communications session.
 20. The medium of claim 13 whereinthe one or more code segments are further configured to: detectavailability of the first connectivity type for communications betweenthe user system and the accessible system; and establish a thirdcommunications session between the user system and the accessiblesystem, the third communication session leveraging the firstconnectivity type, automatically in response to the detectedavailability of the first connectivity type. 21.-30. (canceled)